Isayo Arkindra
Mercurialis Inc.
   |
Posted - 2008.12.28 12:06:00 -
[1]
While I haven't got these issues at all, I feel sorry for you guys who do. I've been around EVE for eight years now so I've gone through similar issues a couple of times. Most of the times it's actually been outside of CCPs area - as in the ISPs very close to the servers.
There are a lot of technicians etc in the playerbase and it tends to go faster if you put the information public rather than sending it over to CCP only. So why not do both?
Do a tracert from your computer to 87.237.38.200 - this'll allow everyone to find the common factors (if there are any) between you all. Again, the last time that I remember this happening it turned out to be a major screwup with Tiscali. So do the tracert, post the results here. Also do the pingplotter thing and keep it running so there's some nice data around the events. Upload the image to a site that can host it (ImageShack maybe?) and post the URL here.
I did the above mentioned things, and noticed that when my packets are running through they end up beeing routed through two different routers inside Tiscaly. One of them resulting in a 20% packet loss - but it's only taking this route on every 3rd or 4th try.
The one that works is xe-1-0-0.lon20.ip.tiscali.net [89.149.186.81], the one that doesn't work is xe-2-0-0.lon20.ip.tiscali.net [89.149.186.85]. Both of these are the router that's handing over trafic to Telecity - the service provider that CCP seems to be using in London.
Obviously - when the packet loss occurs, the ping results on the later routers goes into crazy mode. I'm having results of all the way up to 302ms. I guess this could explain why, recently, I'm having tiny freeze ups in the game every so often. I don't get disconnected, it just "pauses" my display/input for a second or two.
So to stick to what I've just posted ..
 Originally by: "The route that works"
1 2 ms 1 ms 1 ms 192.168.0.254
2 1 ms 2 ms 1 ms ge-8-B-dr1.a1.mlm.ownit.se [10.100.100.1]
3 2 ms 2 ms 1 ms 10ge-1-2-cr1.a1.mlm.ownit.se [89.253.100.149]
4 12 ms 11 ms 11 ms ge-2-1-cr1.a1.sth.ownit.se [84.246.88.129]
5 11 ms 11 ms 11 ms 10ge-2-2-cr2.a1.sth.ownit.se [84.246.88.150]
6 11 ms 11 ms 12 ms ge-3-1-0-5.stk30.ip.tiscali.net [213.200.72.57]
7 43 ms 42 ms 43 ms xe-1-0-0.lon20.ip.tiscali.net [89.149.186.81]
8 50 ms 42 ms 42 ms telecity-redbus-gw1.ip.tiscali.net [213.200.79.130]
9 43 ms 42 ms 43 ms 532-dist65-01.lon3.telecity.net [217.20.44.226]
10 43 ms 42 ms 43 ms ipt-ccp-games-1-as35834.lon3.telecity.net [217.20.44.138]
11 42 ms 41 ms 42 ms 87.237.38.200
Originally by: "The route that's got packet loss"
1 2 ms 1 ms 1 ms 192.168.0.254
2 2 ms 2 ms 1 ms ge-8-B-dr1.a1.mlm.ownit.se [10.100.100.1]
3 2 ms 2 ms 2 ms 10ge-1-2-cr1.a1.mlm.ownit.se [89.253.100.149]
4 13 ms 11 ms 11 ms ge-2-1-cr1.a1.sth.ownit.se [84.246.88.129]
5 12 ms 11 ms 11 ms 10ge-2-2-cr2.a1.sth.ownit.se [84.246.88.150]
6 11 ms 11 ms 11 ms ge-3-1-0-5.stk30.ip.tiscali.net [213.200.72.57]
7 43 ms 42 ms 42 ms xe-2-0-0.lon20.ip.tiscali.net [89.149.186.85]
8 47 ms 43 ms 43 ms telecity-redbus-gw1.ip.tiscali.net [213.200.79.130]
9 43 ms 43 ms 46 ms 532-dist65-01.lon3.telecity.net [217.20.44.226]
10 43 ms 43 ms 43 ms ipt-ccp-games-1-as35834.lon3.telecity.net [217.20.44.138]
11 42 ms 42 ms 42 ms 87.237.38.200
While posting this, I also noticed a third router beeing used at Tiscaly - this one has packet loss as well, but not as severe (between 3-5%). That one's inlucded on the pingplotter view. It's constantly my 7th hop that's changing around - so for me it's a very clear indicator that it's Tiscaly causing my issues.
PingPlotter results
__________
|